-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to React Native v0.59.0 #741
Conversation
Adapted from a newly created demo app via: `react-native init`
First tests looks good. I'll also test integration with WPiOS. @SergioEstevao is there a branch for this? |
WPiOS looks good too. I'll publish a branch if there's any. |
Hey @hypest, nice work here :)
|
Thanks for taking this for a test drive @marecar3 ! Nice find about the focus. What I actually see is that the focus seems to move as you scroll even! This can "explain" why the focus moves when the keyboard comes up and such. Quite frustrating. Will look into it. |
I couldn't reproduce any of those issues on iOS. (both example and WPiOS apps). I do think that is necessary a new JS Bundle, since currently WPiOS is broken without metro running. |
Opent WPiOS PR: wordpress-mobile/WordPress-iOS#11271 |
There's this issue on the ReactNative repo facebook/react-native#23916 that is probably related to the scrolling/focus issue we're seeing here. |
I pushed c2d1889 that has a workaround for the losing-focus-on-scroll issue, by disabling the Flatlist's optimization of destroying the views when they get out of the viewport. That's a real bummer of course but, we apparently will need to implement a proper support for Views recycling that is more compatible with focus preservation. For reference, this is the PR that sets that prop to default true for Android in React Native: Rachelmorrell/react-native#170 Chances are that there are more factors at play here and this becomes an issue with v0.59.0 but, for now it's an OK workaround for us until we put in proper support for views recycling. |
@marecar3 , I think the No1, No2, No3 findings you mentioned got fixed with c2d1889. Can you recheck? Regarding finding No4 ( |
@hypest nice that we fixed those, I will try the branch now and will come back with the new feedback. |
Hey @hypest I have pointed this PR to the latest GB Not sure if it's something wrong only on my laptop |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
iOS side looks good and WPiOS PR is ready and waiting! 🎉
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @hypest I have checked, everything is working great now !!! nice one 🍾
Probably It would be good to update this branch with the latest develop
and to point it to the latest Gutengerg rnmobile/develop
branch so that we can have everything up to date.
I've updated from current Fortunately, that fixed one known issue. The Android demo app and wpandroid look good during my testing. @SergioEstevao can you do another round of smoke testing on the iOS side of things to make sure this will not disrupt anything when we merge? Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Working great!
This PR tracks the effort to upgrade to the v0.59.x version of React Native.
Known issues:
On the android side of things, the demo app fails to keep the title block to its original value. It seems that there is a "stray". Seems fixed after updating with a recentAppContainer.setTitleAction()
call that empties the title, but trying to follow the callstack in the debugger shows things that don't make sense. Looks like the JS files could be mixed up somehow. Thing is, the RN app works fine inside wpandroid so, we can probably tackle this issue separatelydevelop
.Filed a bug report on the
react-native
repo: facebook/react-native#23955